Release notes

2025r9

Additional restriction units in rights API

In this version, new units were added to the maximum number of runs per unit restriction. Since this restriction is part of the rights API when creating or updating rights in contract entries, the units have also been added to the API.

The units are now present in the YAML and can be used in the maxRunsPerUnitRestrictions object, such as in the POST /contractEntries call.

An example of a new unit in the POST /contractEntries call:

            "maxRunsPerUnitRestrictions": [
        {
          "fromDate": "2014-01-01",
          "toDate": "2025-04-30",
          "maxNumberOfRuns": {
            "maxNumberRunsPerUnit": 3,
            "unit": "Weekdays"
          },
          "includeFreeReruns": true
        }
      ],

API developers

Latest YAML available via: GET /api

At line 2353, the units were added to the unit properties of the MaxNumberOfRuns schema.

YAMLs can be compared in more detail using: TextCompare

2025r5

Error message for runs of exploitation right templates in rights API

Previously, the business API service crashed when using the rights API and a GET /exploitationRights/{exploitationRightID}/runs call was sent with an exploitationRightID that corresponded to an exploitation right template. This was because templates do not have actual runs like regular rights.

From this version, when a call is sent with an exploitation right template ID in the URL, a 422 error is returned:

{
    "statusCode": "422",
    "message": "Operation cannot be completed due to violations",
    "timestamp": "2025-05-14T14:23:00Z",
    "concept": "Runs",
    "id": "3139963",
    "errors": [
        {
            "errorCode": "RIGHTS-00039",
            "description": "$_Exploitation right templates do not contain run data",
            "data": []
        }
    ]
}

The YAML was not updated for this change.